feat(cmd): add set-up command for BYOC container configuration#196
Conversation
Introduces a new `devsy set-up` command that applies devcontainer lifecycle hooks (postCreateCommand, postStartCommand) and containerEnv variables to an already-running container via `docker exec`, without building an image.
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 3 minutes and 44 seconds.Comment |
Summary
Adds a new
devsy set-upcommand that applies devcontainer.json configuration (lifecycle hooks and containerEnv) to an already-running container without building an image. This enables BYOC (Bring Your Own Container) workflows where users have pre-existing containers and want to apply devcontainer lifecycle hooks viadocker exec.The command accepts
--container(required),--config(optional path to devcontainer.json), and--workspace-folder(optional workspace path inside the container). It parses the devcontainer.json and executes postCreateCommand and postStartCommand hooks with containerEnv variables passed as-eflags todocker exec.